Skip to content

Dev#11

Merged
PsicoThePato merged 3 commits into
mainfrom
dev
Jul 16, 2025
Merged

Dev#11
PsicoThePato merged 3 commits into
mainfrom
dev

Conversation

@PsicoThePato

@PsicoThePato PsicoThePato commented Jul 16, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • New Features

    • Added a comprehensive "How to be a builder on Torus" guide to assist new contributors with step-by-step onboarding.
    • Introduced a detailed "Setup a Wallet" guide, including instructions for installing and configuring SubWallet and alternative wallet options.
    • Added a new "How-to Guides" section to the sidebar navigation for easier access to practical documentation.
  • Documentation

    • Updated package installation commands and import statements in client and server agent documentation to use the new SDK package name.
    • Improved and expanded how-to documentation with clear, actionable steps and resource links.

@coderabbitai

coderabbitai Bot commented Jul 16, 2025

Copy link
Copy Markdown

Walkthrough

The changes introduce a new "How-to Guides" section in the Astro sidebar configuration and add three new comprehensive how-to documentation pages: a general builder's guide, a participation guide, and a wallet setup guide. Additionally, existing agent client/server documentation is updated to use a new SDK package name in installation and import statements.

Changes

Files/Paths Change Summary
astro.config.mjs Sidebar updated: "Capability Permissions" entry expanded; new "How-to Guides" section and item added.
src/content/docs/agents/client.mdx
src/content/docs/agents/server-setup.mdx
Updated package installation and import statements from @torus-network/torus-ts-sdk to @@torus-network/sdk.
src/content/docs/how-to-guides/how-to-guides.mdx
src/content/docs/how-to-guides/how-to-take-part.mdx
src/content/docs/how-to-guides/setup-a-wallet.mdx
Added three new how-to guide documentation pages for Torus builders and wallet setup.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DocsSite
    participant Sidebar
    participant Guides

    User->>DocsSite: Visit documentation
    DocsSite->>Sidebar: Render navigation
    Sidebar-->>User: Show new "How-to Guides" section
    User->>Guides: Select "Setup a Wallet" or builder guide
    Guides-->>User: Display step-by-step instructions
Loading

Possibly related PRs

  • Dev #7: Also modifies the sidebar navigation in astro.config.mjs, including the "Capability Permissions" entry.
  • Dev #9: Updates the Astro sidebar configuration, focusing on different sections but overlapping in sidebar structure changes.

Poem

🐇
A sidebar grows, new guides appear,
With wallet wisdom, builders cheer.
SDK imports now align,
Step-by-step, the docs refine.
Torus agents, onward bound—
In helpful guides, solutions found!

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🔭 Outside diff range comments (1)
src/content/docs/how-to-guides/how-to-take-part.mdx (1)

1-92: Duplicate content detected - consolidate or differentiate.

This file appears to contain identical content to src/content/docs/how-to-guides/how-to-guides.mdx. Having duplicate content can cause confusion and maintenance issues.

Consider one of these approaches:

  1. Remove duplicate: If both files serve the same purpose, keep only one
  2. Differentiate content: If they serve different purposes, modify the content to be distinct
  3. Create redirects: If both URLs need to work, create a redirect from one to the other

The current setup violates the DRY principle and could lead to content synchronization issues.

♻️ Duplicate comments (1)
src/content/docs/agents/client.mdx (1)

28-28: Verify the package name with double @@ prefix.

Same issue as in server-setup.mdx - the package name @@torus-network/sdk uses an unusual double @@ prefix that could cause installation failures.

Also applies to: 34-34, 78-78, 304-304, 417-417

🧹 Nitpick comments (6)
astro.config.mjs (1)

102-111: Clean up commented-out duplicate code.

The new "How-to Guides" section is properly structured, but the commented-out duplicate entry should be removed.

Apply this diff to clean up the commented code:

         {
           label: "How-to Guides",
           items: [
             { label: "Setup a wallet", slug: "how-to-guides/setup-a-wallet" },
-            // {
-            //   label: "Setup a wallet",
-            //   slug: "how-to-guides/setup-a-wallet",
-            // },
           ],
         },
src/content/docs/how-to-guides/setup-a-wallet.mdx (5)

52-54: Minor typo: “you browser” → “your browser”

-1.  **Open the SubWallet extension in you browser**:   
+1.  **Open the SubWallet extension in your browser**:   

84-86: Spelling: “successfull” → “successful”

-        Below is a reference image of a successfull account created in the
+        Below is a reference image of a successful account created in the

89-90: Image alt-text typo

Alt text currently reads “…succesfully…”.

-![SubWallet account succesfully created](/images/how-to-guide/setup-wallet/subwallet-created-successfully.png)
+![SubWallet account successfully created](/images/how-to-guide/setup-wallet/subwallet-created-successfully.png)

97-101: Grammar & casing tweaks for the burger-menu instruction

Small readability fixes and consistent “SubWallet” casing.

-1. **Open the Subwallet Setup**:  
-  Click in the three bars(**☰**) on the top left corner of the subwallet extension.
+1. **Open the SubWallet menu**:  
+  Click the three bars (**☰**) in the top-left corner of the SubWallet extension.

108-111: Typo: “mihgt” → “might”

-    You mihgt have to scroll down to find Torus in the list.
+    You might have to scroll down to find Torus in the list.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a4bf32c and f33fc0d.

⛔ Files ignored due to path filters (6)
  • public/images/how-to-guide/setup-wallet/subwallet-created-successfully.png is excluded by !**/*.png
  • public/images/how-to-guide/setup-wallet/subwallet-done-torus-setup.png is excluded by !**/*.png
  • public/images/how-to-guide/setup-wallet/subwallet-extension-activated.png is excluded by !**/*.png
  • public/images/how-to-guide/setup-wallet/subwallet-open-setup.png is excluded by !**/*.png
  • public/images/how-to-guide/setup-wallet/subwallet-search-torus-network.png is excluded by !**/*.png
  • public/images/how-to-guide/setup-wallet/subwallet-select-config-to-add-network.png is excluded by !**/*.png
📒 Files selected for processing (6)
  • astro.config.mjs (2 hunks)
  • src/content/docs/agents/client.mdx (4 hunks)
  • src/content/docs/agents/server-setup.mdx (2 hunks)
  • src/content/docs/how-to-guides/how-to-guides.mdx (1 hunks)
  • src/content/docs/how-to-guides/how-to-take-part.mdx (1 hunks)
  • src/content/docs/how-to-guides/setup-a-wallet.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/how-to-guides/setup-a-wallet.mdx

[grammar] ~52-~52: Ensure spelling is correct
Context: ... 1. Open the SubWallet extension in you browser: Click on the SubWall...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~110-~110: Ensure spelling is correct
Context: ...your list of active networks. You mihgt have to scroll down to find Torus in th...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (2)
astro.config.mjs (1)

40-50: LGTM - Clean reformatting.

The reformatting of the "Capability Permissions" entry from single-line to multi-line format improves readability and consistency with other entries.

src/content/docs/how-to-guides/how-to-guides.mdx (1)

1-92: Well-structured guide with comprehensive coverage.

The guide provides an excellent step-by-step walkthrough for builders wanting to participate in the Torus Network. The structure is logical and the content is well-organized.


```sh
npm install @torus-network/torus-ts-sdk
npm install @@torus-network/sdk

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify the package name with double @@ prefix.

The package name @@torus-network/sdk uses an unusual double @@ prefix, which is not standard for npm packages. Standard scoped packages use a single @ prefix (e.g., @torus-network/sdk). This could cause installation failures.

Please verify if this is the correct package name or if it should be @torus-network/sdk instead.

Also applies to: 37-37, 446-446


🏁 Script executed:

#!/bin/bash
# Check if the package exists on npm registry
npm view @@torus-network/sdk --json 2>/dev/null || echo "Package not found with @@"
npm view @torus-network/sdk --json 2>/dev/null || echo "Package not found with single @"

Length of output: 4723


Correct npm package name prefix

The npm package @@torus-network/sdk is invalid (npm scoped packages use a single @). The correct package name on the registry is @torus-network/sdk. Please update all occurrences:

• src/content/docs/agents/server-setup.mdx: lines 31, 37, 446

Replace:

- npm install @@torus-network/sdk
+ npm install @torus-network/sdk
🤖 Prompt for AI Agents
In src/content/docs/agents/server-setup.mdx at lines 31, 37, and 446, the npm
package name is incorrectly written as @@torus-network/sdk with a double '@'.
Replace all occurrences with the correct scoped package name @torus-network/sdk
using a single '@' to fix the invalid package reference.


Every agent begins with a wallet that can sign transactions.

👉 [How to create a wallet](/how-to-guides/set-up-wallet)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify that linked guides exist.

Many of the linked how-to guides appear to reference pages that don't exist yet. This could create a poor user experience with broken links.

Also applies to: 26-27, 35-36, 44-45, 53-54, 62-62, 70-71, 84-85


🏁 Script executed:

#!/bin/bash
# Check if the linked guide files exist
guides=(
  "how-to-guides/set-up-wallet"
  "how-to-guides/register-agent"
  "how-to-guides/apply-to-be-whitelisted"
  "how-to-guides/create-permission"
  "how-to-guides/edit-permission"
  "how-to-guides/create-capabilities"
  "how-to-guides/delete-capabilities"
  "how-to-guides/create-signal"
  "how-to-guides/receive-emissions"
  "how-to-guides/agent-api"
  "how-to-guides/host-agent"
  "how-to-guides/connect-to-chain"
  "how-to-guides/respond-to-signal"
)

for guide in "${guides[@]}"; do
  if [ -f "src/content/docs/$guide.mdx" ] || [ -f "src/content/docs/$guide.md" ]; then
    echo "$guide exists"
  else
    echo "$guide not found"
  fi
done

Length of output: 3711


Missing linked how-to guide pages
The following links in src/content/docs/how-to-guides/how-to-guides.mdx point to guides that don’t exist, which will result in broken links:

  • /how-to-guides/set-up-wallet (line 18)
  • /how-to-guides/register-agent (lines 26–27)
  • /how-to-guides/apply-to-be-whitelisted (lines 35–36)
  • /how-to-guides/create-permission (lines 44–45)
  • /how-to-guides/edit-permission (lines 53–54)
  • /how-to-guides/create-capabilities (line 62)
  • /how-to-guides/delete-capabilities (lines 70–71)
  • /how-to-guides/create-signal (lines 84–85)
  • /how-to-guides/receive-emissions
  • /how-to-guides/agent-api
  • /how-to-guides/host-agent
  • /how-to-guides/connect-to-chain
  • /how-to-guides/respond-to-signal

Please add the corresponding .mdx (or .md) files under src/content/docs/how-to-guides/ for each of these topics, or update/remove the links to point at existing pages.

🤖 Prompt for AI Agents
In src/content/docs/how-to-guides/how-to-guides.mdx around lines 18 to 85,
several links point to how-to guide pages that do not exist, causing broken
links. To fix this, create the missing .mdx or .md files for each linked topic
under src/content/docs/how-to-guides/, or alternatively update or remove the
links to point to existing valid pages to ensure all links are functional.

Comment on lines +28 to +33

1. **Download the Extension**
Visit the [SubWallet download page](https://www.subwallet.app/download.html) and download the appropriate version of the extension for your browser (Chrome, Brave, Firefox, or Microsoft Edge).

3. **Activate/Pin the Extension**
In some cases, you may need to activate the extension manually. Refer to the [SubWallet documentation](https://docs.subwallet.app/main) for instructions.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Step numbering skips “2.” – update for clarity

Readers will wonder whether an instruction is missing because the list jumps from “1.” to “3.”. Renumber or convert to automatic Markdown numbering.

-3.  **Activate/Pin the Extension**  
+2.  **Activate/Pin the Extension**  
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. **Download the Extension**
Visit the [SubWallet download page](https://www.subwallet.app/download.html) and download the appropriate version of the extension for your browser (Chrome, Brave, Firefox, or Microsoft Edge).
3. **Activate/Pin the Extension**
In some cases, you may need to activate the extension manually. Refer to the [SubWallet documentation](https://docs.subwallet.app/main) for instructions.
1. **Download the Extension**
Visit the [SubWallet download page](https://www.subwallet.app/download.html) and download the appropriate version of the extension for your browser (Chrome, Brave, Firefox, or Microsoft Edge).
2. **Activate/Pin the Extension**
In some cases, you may need to activate the extension manually. Refer to the [SubWallet documentation](https://docs.subwallet.app/main) for instructions.
🤖 Prompt for AI Agents
In src/content/docs/how-to-guides/setup-a-wallet.mdx around lines 28 to 33, the
numbered list skips from step 1 to step 3, which can confuse readers. Fix this
by either renumbering the steps sequentially or by using automatic Markdown
numbering (e.g., using "1." for all steps) so the list renders with correct
numbering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants